Make it clearer how the user can control compiler optimization #530
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
awvwgk
added
build: cmake
awvwgk
requested changes
Sep 19, 2021
awvwgk
approved these changes
Sep 20, 2021
jvdp1
approved these changes
Sep 20, 2021
Co-authored-by: Jeremie Vandenplas <[email protected]>
Co-authored-by: Jeremie Vandenplas <[email protected]>
This was referenced Sep 27, 2021
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These edits to the README attempt to offer simple guidance on compiling stdlib with optimization flags.
In this discussion here it became clear that not everyone understands how to apply compiler optimizations to stdlib, although the discussion shows that is quite important for performance.
I think some simple pointers would help users who do not have much experience with build tools (like me!).